home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Papercom - Logiciel Cartes De Visite
/
Papercom - Logiciel Cartes De Visite.iso
/
manuel
/
acrobat
/
abcpydoc.ini
< prev
next >
Wrap
INI File
|
1996-09-24
|
15KB
|
317 lines
;*******************************************************************************
;
;ABCPYDOC.INI - This file is an example file that shows how to provide the
; "blind-copy" capability for use with Adobe Acrobat installations.
;
;NOTE: Do NOT use this file for blind-copy. It is meant only as an example.
;*******************************************************************************
;
;Blind-copy capability provides a mechanism where a customer may add to
;an installation set. To trigger the blind-copy mechanism, a file named
;ABCPY.INI (Adobe Blind CoPY initialization file) must exist in the same
;directory as the installer (SETUP.EXE) for Acrobat, whether for the individual
;Acrobat products or the Acrobat 3.0 "umbrella".
;
;ABCPY.INI is formatted similar to an .INI file, with section names that must
;match values set in ACROINST.INI (a hidden file used by Acrobat installations).
;For example, if a customer needs the blind-copy capability for an Acrobat Reader
;installation, a section in ABCPY.INI must be named [ReaderBlindCopy]. If
;Acrobat Exchange is the product installed, a section named [ExchangeBlindCopy]
;must exist in ABCPY.INI.
;
;There are five types of "object actions" that can be added. 1) A "requirement"
;may be performed, 2) files can be copied, 2) program items or shortcuts
;(depending on the target operating system) can be created, 3) registry entries
;can be created, and 4) INI entries can be created.
;
;To have an action performed on these blind-copy objects, there are several
;entries that must be made within the product's blind-copy section. First,
;there must be a key named "NumberOfGroups" and this key must have a value
;of 1 or more.
;
;For each "group", there will need to be entries for operating system platform,
;target destination location, source location, and an optional entry for a
;"group" name which is used for the group name when program items or shortcuts
;are created.
;
;By reviewing the example section in this file, the entries for each group are:
;Group<X>Platform=All
;Group<X>DestDir=Org
;Group<X>Loc=Org
;Group<X>Name=
;
;where <X> is replaced with the number of a specfic group.
;NOTE: The value for the group can be not larger than the number of groups as
; defined in NumberOfGroups key in this section.
;
;The platform key must contain a value contained in the following set:
;(All, Win32, Win16, Win95, WinNT, !WinNT).
;All means this group is targeted to all Windows operating system.
;Win32 means the target platform is Windows 95 or Windows NT.
;Win16 means the target platform is only 16 bit Windows (3.1x).
;Win95 means only Windows 95.
;WinNT means only Windows NT
;!WinNT means the target platform is All except Windows NT.
;
;Group<X>DestDir contains the target detination directory name.
;
;Group<X>Loc is the source location relative to the main installation directory
;(i.e. on the source media of the installation set, NOT where the user chose to
;install Acrobat).
;
;All remaining keys are used for performing certain actions.
;Each group can then have entries for the five "object actions" and those actions
;use the group settings for determining the source, destination, etc. Below is
;a description of how to set these up correctly.
;
;>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
;REQUIREMENTS
;
;To have a "requirement" performed, there must be one line in the group as follows:
;
;Group<X>NumberOfRequirements=<Y>, where <X> is the group number and <Y> is the
;number of requirement actions to be performed for this group. At this time, the
;only supported requirement is running the Windows application REGEDIT.EXE which
;can be used to add registry entries using a pre-defined registry file.
;
;The following shows an example requirement using REGEDIT:
;
;Group2NumberOfRequirements=1
;Group2Requirement1=REGEDIT
;Group2RegEditFile=Extra\Extra32.REG
;
;The key Group<X>RegEditFile=<.REG file> must exist on the users system in a
;sub-directory of the path where Acrobat was installed. This .REG file will
;then be run via REGEDIT.EXE.
;
;>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
;FILE COPYING
;
;To have a file "blind copied" during installation, there must be a key named
;Group<X>NumberOfFiles, and the value of this key must be the number of files to
;be copied from this source location to the group's target destination as defined
;in the Group<X>DestDir and Group<X>Loc keys.
;
;For each file to be copied, a key of the following format must be defined:
;Group<X>FileName<Y>, where <X> is the group number and <Y> is the file number.
;NOTE: The file number cannot be greater than the number of files value.
;
;NOTE: There is no mechanism to rename files as they are copied.
;
;NOTE: Files will be directly copied. The blind-copy mechanism would not know
; which decompression scheme to use.
;
;<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
;PROGRAM ITEMS AND SHORTCUTS
;
;To create a program item or shortcut, a key must be defined containing the number
;of "icons" to be created.
;
;If the number is one or more, a key in the following format must be defined:
;Group<X>Icon<Y> (see notes above regrarding numbering).
;
;The value for these keys is rather cryptic, so please bear with this discussion.
;This type of object action requires a comma-delimited (i.e. separated by commas)
;value that has a variable number of parameters depending on the value of the first
;parameter.
;
;The first parameter of the value must be either SYTLE1 or STYLE2.
;STYLE1 is used when the object referred to is an executable or an automatically
;launched file (i.e if the file's extension automatically launches the correct
;executable).
;STYLE2 is used when the object referred to requires a primary executable to launch
;the second file (e.g. NOTEPAD.EXE is often used for launching a ReadMe file).
;
;Once the STYLE<X> is defined, the second portion refers to the working directory
;for the file named in the third portion. There are a limited number of values allowed
;for this second parameter. If the first character is a '$' then the following values
;are accepted: Windows or WindowsSystem. These refer to the directory where Windows is
;installed or the Windows System directory, respectively.
;
;As stated above, the third parameter is the name of the executable file (or automatically
;launched file is that is appropriate).
;
;The fourth parameter is the literal text that will be displayed in the Windows UI that
;describes the main file (for STYLE1 this is the file referred to in the 3rd parameter,
;for STYLE2 it is the file referred to in the 7th parameter).
;
;For the fifth parameter (and last for STYLE1 entries), this is a number for the index to
;the icon for Windows to use from the 3rd parameter. This is typically 0 (zero).
;
;STYLE2 entries require two more parameters. The sixth parameter is the location or
;working directory of the file referenced in the seventh and last parameter.
;
;The following explanation of the example entries should clarify most questions.
;
;Group1Icon1=STYLE1,Org,Match.exe,Match,0
;In this example, the above entry will create a program item or shortcut in the same
;folder as was used by the Acrobat installation (because Group1Name is blank). The item
;will display "Match" (the 4th parameter) as the description, and the command line created
;will be for the program named Match.exe that is located in the Org directory below where
;the user chose to put their Acrobat program files. The first icon indexed within Match.exe
;will be used in displaying the item.
;
;Group1Icon2=STYLE2,$Windows,Notepad.exe,Match ReadMe,0,Org,Readme.txt
;Here the entry will create a program item or shortcut in the same folder as was used by
;the Acrobat installation (because Group1Name is blank), for the file named Readme.txt
;that is located in the Org directory below where the user chose to put their Acrobat
;pro